refactor: migrate chess client to React components with puzzles integration#105
refactor: migrate chess client to React components with puzzles integration#105
Conversation
… control for CI builds
F-Hejazi
force-pushed
the
chess-client-migration
branch
from
0ce4808 to
4566003
Compare
|
I noticed your CI/CD build function isn't working... I'd recommend comparing this to main's test cases for react-ystemandchess before continuing with reviewing your code, and if there are no discrepancies, then it would be ideal to update the test functions for react-ystemandchess so that it accomodates for your new changes. if there IS discrepancies, I would suggest changing the test cases to the version you find in main, and seeing if that works. test("stub: renders LessonOverlay without crashing", () => { |
F-Hejazi
force-pushed
the
chess-client-migration
branch
from
4c6148c to
17817f0
Compare
|
While this branch runs, it would be ideal to work on the conflicts this branch has (likely through pulling the recent updates that were made to main) |
|
Everything runs without issue. You should be ready to merge now! |
|
I've checked your updates, and they all work without issue. You are free to merge when you are ready. |
3 participants
This PR migrates the chess functionality from the standalone client to native React components, removing iframe dependencies and consolidating all chess logic within the React application for seamless platform integration.
Key Changes
useChessSockethook to manage Socket.IO connections, real-time game state synchronization, move validation, and multiplayer coordination for both lessons and puzzlesChessBoardcomponent andLessonOverlay.tsxto leverage the new socket hook, replacing postMessage communication with direct React state managementPuzzles.tsxfrom iframe-based implementation to native React with computer opponent automation, puzzle move validation, and integrated hint systemchessClientfolder entirely, eliminating the Live Server dependency and external code maintenance